🐛fix: #151 - Fix the UTF malformated #158
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
laudeco
requested review from
amstuta,
deathiop,
mxpetit and
rbeuque74
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The problem
Yesterday we had the following issue with the OVH API
Note
Do not pay attention to the Line (we hotfixed the line on our environment)
Fix
To fix the issue we ignored the malformed UTF8 json by using the flags of
json_decodehttps://www.php.net/manual/en/function.json-decode.php https://www.php.net/manual/en/json.constants.php#constant.json-invalid-utf8-ignoreissue
The issue #151 is fixed by the current MR